explicitly mention regarding the nonce#3
Merged
Ishita-02 merged 1 commit intoyield-agentkit-privyfrom Mar 31, 2026
Merged
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request updates the Privy transaction processing documentation to clarify how to handle Ethereum nonces when submitting multiple sequential transactions. The changes emphasize that the MCP may return all transactions with the same nonce, and provides explicit instructions for incrementing the nonce per transaction step. This is critical to ensure transactions are processed correctly and avoid nonce collisions.
Documentation improvements for nonce handling:
stepIndex, including examples for how to compute the correct nonce. [1] [2]privy-transactions.mdandsemi-autonomous.mdto show the correct nonce handling for each step, ensuring implementers understand the required process. [1] [2]